Skip to content

Upgrades composer to use mujoco==3.10.0#317

Merged
juelg merged 2 commits into
masterfrom
upgrade-mjspec
Jul 12, 2026
Merged

Upgrades composer to use mujoco==3.10.0#317
juelg merged 2 commits into
masterfrom
upgrade-mjspec

Conversation

@wpumacay

Copy link
Copy Markdown
Collaborator

Description

  • Upgrades composer.py to use the latest version of the MjSpec API
  • Updates mujoco version to 3.10.0 (latest atm)

Here is a video of the cartesian control example for the fr3, seems to work just fine.

Kooha-2026-07-09-23-45-32.mp4

@juelg , as I mentioned on the lab, the changes are mostly improvements (apart from the breaking changes to the spec API), but it would be better if you can run your tests and also run your benchmarks to see that nothing iffy is going on.

Also, have to make sure that the wildcard for libmujoco.so.* does the trick when building the manylinux wheels.

@wpumacay wpumacay requested a review from juelg July 10, 2026 06:46
@wpumacay

Copy link
Copy Markdown
Collaborator Author

@juelg , seems there's some other places I missed that also use mjspec. Will check the failed workflow's outputs and update the files

- With the new mjspec API, when attaching an object, the old reference
  spec (e.g. child_spec) is updated as well, and its names changes. This
  was causing the prefix being duplicated and was making it fail when
  searching for a specific reference in the new spec
@juelg juelg merged commit d825bb6 into master Jul 12, 2026
6 checks passed
@juelg juelg deleted the upgrade-mjspec branch July 12, 2026 01:01
tenfoldpaper pushed a commit that referenced this pull request Jul 12, 2026
Upgrades composer to use mujoco==3.10.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants